-
Couldn't load subscription status.
- Fork 90
fix: properly setting diagnostic errors when opening and closing code mirror #8631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This is a follow-up to #7166 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fixed a recurrence of the bug where diagnostics would disappear on open or close of the code pane if they were of the lint or runtime type, and also fixed the behavior in my PR after merging these changes in. Thanks!
|
@nadr0 I'd recommend reverting the two automated "Update snapshots" commits then immediately pulling in the latest |
|
Closing this because it didn't actually block Frank and to properly fix this we need to solve the LSP/KCL run time errors/Lint errors globally. |
Issue
When you open kcl editor the previous diagnostics are cleared and safe parse is ran and it is confusing.
Implementation
We need to not clear the diagnostics when we unmount the kcl editor. We need to call a higher level function than safeParse which is executeCode because that computes more diagnostics.
safeParse only computes parse errors
lintAst computes the LSP errors
executeAst computes the runtime KCL errors.